Systems and methods of mobile database management and sharing

ABSTRACT

Systems and methods of mobile database management and sharing are provided which include at least one mobile database and a first electronic circuit in communication with the mobile database. The system segments the mobile database into a plurality of database segments and indexes the plurality of database segments. The system sends one or more of the plurality of database segments to a second electronic circuit over a private secured communication protocol. One or both of the first and second electronic circuit may be housed within one or more mobile devices. Disclosed systems and methods include processing a database sharing request received from at least one mobile device wherein the database sharing request requests sharing of one or more of the plurality of database segments. A mobile device containing a database management and sharing system is also provided which includes a shared mobile database and one or more proxy entities related to the shared mobile database. At least some of the plurality of database segments are sent via the one or more proxy entities to one or more separate mobile devices and stored in the mobile device and the one or more separate mobile devices.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a non-provisional of and claims priority to U.S.Patent Application No. 62/676,393, filed May 25, 2018, which is herebyincorporated by reference in its entirety.

FIELD

The present disclosure relates to systems and methods of mobile databasemanagement and sharing and, more particularly, to database sharingmethods of synchronizing data used in mobile devices.

BACKGROUND

File sharing, and data management in general, is becoming a majorchallenge in today's world. With all of the various types of files ondifferent devices such as personal computers, personal digitalassistants, or mobile devices, the management of data in an efficientmanner from device-to-device is a challenge for users, for mobileservice providers, and mobile devices designers/manufacturers.

Many applications require the ability to download information from aninformation repository and operate on this information even when out ofrange or disconnected. An example of this is your contacts and calendaron the phone. In this scenario, a user would require access to updateinformation from files in the home directories on a server or customerrecords from a database. This type of access and work load generated bysuch users is different from the traditional workloads seen inclient-server systems of today.

Mobile users must be able to work without a network connection due topoor or even non-existent connections. A cache could be maintained tohold recently accessed data and transactions so that they are not lostdue to connection failure. Users might not require access to truly livedata, only recently modified data, and uploading of changing might bedeferred until reconnected.

Other issues that arise in this context are that bandwidth must beconserved (a common requirement on wireless networks that charge permegabyte or data transferred); mobile computing devices tend to haveslower CPUs and limited battery life; and users with multiple devices(e.g. smartphone and tablet) need to synchronize their devices to acentralized data store. This may require application-specific automationfeatures. In addition, users may change location geographically and onthe network. Usually, dealing with this is left to the operating system,which is responsible for maintaining the wireless network connection.

In the context of data files in general, files worked on at one locationby a user may not be accessible from a device at another location. Forexample, a user working at home may have files left there on a homecomputer that are not accessible from a computer at work. Data on onedevice may be lost because the user failed to regularly back-up the datafiles on the device. In other situations, short of forwarding each fileor email to another account, switching accounts with an internet serviceprovider may cause a user to lose their emails and other personal filesresident on that ISPs server. All of these problems with dataportability, management, and access create inefficiencies for a user.

Some known systems have tried to address these issues. In the photosharing context, websites have allowed users to load files to thewebsite to share among multiple devices and multiple users. This doesallow some access to images when the user is not at his/her homecomputer and to share photos with users at remote locations. The sharingof files, however, among multiple users, especially over mobile devicesis typically limited to low-resolution versions of the original images,and this sharing of lower quality files may cause a user difficulty inviewing the image.

Additionally, there is no data persistence as the files on the servermay be deleted after a certain period of inactivity. In systems whereusers use peer-to-peer sharing or email picture files to each other,images may be lost or hard to track down because the original email waslost or poorly organized among the users' files. Additionally, dynamicupdating of shared files is not present. The data or file is copied onetime and is then static on the sharee's system.

Currently, mobile data capture devices (MDCD) are used to capture data.Mobile data capture devices may include, for example, cellulartelephones, personal digital assistants (PDAs), digital cameras, digitalvideo recorders, and so on. MDCDs are used in different environments andin different industries to capture, store, and process different typesof data. Users may desire to take actions including querying, managing,and protecting the data captured on the MDCD. However, MDCDs havetypically been limited in the actions that they can perform. Typically,many actions related to database management have only been available atthe local mobile device level which is dependent on the device memoryand storage options.

In view of the issues discussed above, there is a need for systems andmethods that provide the ability to download information from aninformation repository and operate on this information even when out ofrange or disconnected. There is a need for a mobile database that canstore information while conserving bandwidth. There is also a need for amobile database that that allows files worked on at one location by auser to be accessible from a device at another location. Finally, thereis a need for mobile database sharing and management systems thatprovide data persistence and dynamic updating of shared files.

SUMMARY

The present disclosure, in its many embodiments, alleviates to a greatextent the disadvantages of known systems and methods of databasemanagement and sharing by providing database management and sharing formobile devices, over a private, secured communication protocol.Disclosed systems and methods whereby a mobile database is segmented andindexed and one more database segments may be sent among electroniccircuits in mobile devices over a private secured communicationprotocol. A mobile database is either a stationary database that can beconnected to by a mobile computing device (e.g., smartphones and PDAs)over a mobile network, or a database which is actually stored by themobile device. This could be a list of contacts, price information,distance travelled, or any other information. Systems and methodsdescribed herein offer a breakthrough, new concept of databasemanagement and sharing over a private, secured and encrypted network.

The described methods and systems are based on a proprietary IntegratedCircuit (IC) and a mobile software application to split database objectsto segments and sharing them among other mobile devices. These segmentsare sent via private, secured channel to be stored on mobile devicesworldwide and are indexed for restoration purposes. Upon the user'srequest to restore the database item, the system collects all databasesegments from all devices, worldwide and assembles them together torestore the database object. These actions are done in real time and aretransparent for the user. Systems and methods maintain a database item'sbackup on a fire-proof central backup server for immediate restore.

Disclosed systems, methods, and mobile software application providemobile database management and sharing over private, secured network, inreal time. Exemplary embodiments manage databases of all types includingbut not limited to media, textual, graphical and secured communicationinformation. Disclosed systems and methods work with proprietaryintegrated circuits (IC) within mobile devices. Working together withthe IC and the mobile software application, the systems and methodsshare all mobile database types with all other, same mobile ICs that areinstalled on other mobile devices, worldwide, via its own private,secured, encrypted protocol.

Exemplary embodiments divide the database into numerous segments,according to an algorithm, and share them among all other proprietarymobile devices ICs, worldwide, via its network. In exemplaryembodiments, each database segment is encrypted and indexed. Then it isstored in the mobile device's memory, controlled by the system withinthe proprietary IC and the application software. The systems and methodskeep records of all database segments and collect them to the individualmobile device upon user's request in order to restore the database item.The systems and methods may spread all databases across its private,secured network, worldwide, transparent for the user.

Exemplary embodiments perform constant memory optimization to constantlymaintain the optimum free mobile device memory and share it with othermobile devices database segments. The systems and methods move databasesegments dynamically, according to priority, between mobile devices,worldwide. The database segmentation and allocation are done accordingto mobile service bandwidth, mobile device memory capacity andperformance. The systems and methods keep backups for all database itemson a central server.

An important advantage of disclosed embodiments is efficient mobiledevice memory utilization at all times. With this system mobile devicesmemories will be freed for more utilization, the power consumption willbe reduced, and the mobile device processing capabilities dramaticallyincreased. In addition, disclosed embodiments enable better utilizationof the mobile provider band width and data packaging for user'senjoyment, worldwide.

Exemplary embodiments of a mobile database management and sharing systemcomprise at least one mobile database and a first electronic circuit incommunication with the mobile database. The electronic circuit includesa controller, a secured basic input/output (BIOS) system, a memory unit,a radio unit, and an antenna. The system segments the mobile databaseinto a plurality of database segments, the system indexes the pluralityof database segments, and the system sends one or more of the pluralityof database segments to a second electronic circuit over a privatesecured communication protocol. In exemplary embodiments, one or both ofthe first and second electronic circuit is an integrated circuit, andone or both of the first and second electronic circuit may be housedwithin one or more mobile devices.

In exemplary embodiments, the mobile database management and sharingsystem further comprises a database management logic in communicationwith the mobile database for analyzing and processing data received fromthe first electronic circuit. The system may further comprise a circuitlogic in communication with the mobile database for performingoptimization of allocation of the plurality of database segments. Inexemplary embodiments, the system further comprises a circuit controllogic in communication with the mobile database for adjusting databasesegmentation and send and receive parameters. The plurality of databasesegments may be encrypted and stored on one more mobile device memoriesin the one or more mobile devices. In exemplary embodiments, the systemfurther comprises a database assembly logic in communication with themobile database configured to communicate with the one or more mobiledevices to collect and assemble the mobile database using one or moreprivate channels in parallel to sending the one or more of the pluralityof database segments. The system may also include cloud software incommunication with the system.

Exemplary methods of mobile database management and sharing compriseprocessing data received from at least one mobile device containing atleast one electronic circuit, segmenting a mobile database into aplurality of database segments, indexing the plurality of databasesegments, and processing a database sharing request received from atleast one mobile device. The database sharing request requests sharingof one or more of the plurality of database segments, and exemplarymethods further comprise sending the one or more of the plurality ofdatabase segments requested to at least one mobile device over a privatesecured communication protocol. Exemplary systems and methods work inreal-time.

In exemplary embodiments, methods of mobile database management andsharing further comprise communicating the database sharing request to acentral server and communicating database data to the central server inparallel with the database sharing request. Methods may further comprisereceiving a reply to the database sharing request from the centralserver. Exemplary methods include running back-end software on a centralserver, and the back-end software may include artificial intelligence.In exemplary embodiments, methods of mobile database management andsharing further running an error protocol and upon detecting an error,recovering data, repeating the segmentation step, and repeating thesending step.

In exemplary embodiments, a mobile device containing a databasemanagement and sharing system is provided comprising a shared mobiledatabase, one or more proxy entities related to the shared mobiledatabase, and an electronic circuit in communication with the sharedmobile database and the one or more proxy entities. The electroniccircuit includes a controller, a secured basic input/output (BIOS)system, a memory unit, a radio unit, and an antenna. The mobile devicefurther comprises mobile software executed and running on the mobiledevice. The database management and sharing system segments the sharedmobile database into a plurality of database segments and indexes theplurality of database segments. In exemplary embodiments, at least someof the plurality of database segments are sent via the one or more proxyentities to one or more separate mobile devices and stored in the mobiledevice and the one or more separate mobile devices.

In exemplary embodiments, the plurality of database segments is alsostored on a central server. In exemplary embodiments, the one more proxyentities maintain processing requests in a queue. The shared mobiledatabase may contain a partial database of a whole database containedand managed by the database management and sharing system. The mobilesoftware may contain artificial intelligence.

Exemplary methods of sharing data comprise generating a database sharingrequest received from at least one mobile device, the database sharingrequest relating to data in a mobile database, determining that thedatabase sharing request is processed by the mobile database,communicating the database sharing request to a central server,communicating database data to the central server in parallel with thedatabase sharing request, and receiving a reply to the database sharingrequest from the central server. Exemplary methods further compriseencrypting the database data and storing the database data on one moremobile device memories in one or more mobile devices.

Accordingly, it is seen that systems and methods of database managementand sharing are provided. These and other features of the disclosedembodiments will be appreciated from review of the following detaileddescription, along with the accompanying figures in which like referencenumbers refer to like parts throughout.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other objects of the disclosure will be apparent uponconsideration of the following detailed description, taken inconjunction with the accompanying drawings, in which:

FIG. 1 is a schematic of an exemplary embodiment of a mobile databasemanagement and sharing system in accordance with the present disclosure;

FIG. 2 is process flow diagram showing an exemplary embodiment of amobile database management and sharing system and method in accordancewith the present disclosure;

FIG. 3 is a process flow diagram showing exemplary segmentation andindexing processes in accordance with the present disclosure;

FIG. 4 is a schematic of an exemplary embodiment of a mobile databasemanagement and sharing system in accordance with the present disclosure;

FIG. 5 is a perspective view of a mobile database management and sharingsystem and method in accordance with the present disclosure;

FIG. 6 is a process flow diagram showing exemplary segmentation andstorage processes in accordance with the present disclosure;

FIG. 7 is a process flow diagram showing exemplary database objectrestoration processes in accordance with the present disclosure;

FIG. 8 is a schematic of an exemplary embodiment of a mobile databasemanagement and sharing system in accordance with the present disclosure;

FIG. 9 is a schematic of an exemplary embodiment of a mobile databasemanagement and sharing system in accordance with the present disclosure;

FIG. 10 is a schematic of an exemplary embodiment of an electroniccircuit in accordance with the present disclosure;

FIG. 11 is a perspective view of an exemplary embodiment of trackingdevice in accordance with the present disclosure;

FIG. 12 is a perspective view of an exemplary embodiment of a trackingdevice in accordance with the present disclosure;

FIG. 13 is an exploded view of an exemplary embodiment of a trackingdevice in accordance with the present disclosure; and

FIG. 14 is a perspective view of an exemplary embodiment of an affixsensor in accordance with the present disclosure.

DETAILED DESCRIPTION

In the following paragraphs, embodiments will be described in detail byway of example with reference to the accompanying drawings, which arenot drawn to scale, and the illustrated components are not necessarilydrawn proportionately to one another. Throughout this description, theembodiments and examples shown should be considered as exemplars, ratherthan as limitations of the present disclosure.

As used herein, the “present disclosure” refers to any one of theembodiments described herein, and any equivalents. Furthermore,reference to various aspects of the disclosure throughout this documentdoes not mean that all claimed embodiments or methods must include thereferenced aspects. Reference to materials, configurations, directions,and other parameters should be considered as representative andillustrative of the capabilities of exemplary embodiments, andembodiments can operate with a wide variety of such parameters. Itshould be noted that the figures do not show every piece of equipment,nor the materials, configurations, and directions of the variouscircuits and communications systems.

The following includes definitions of selected terms employed herein.The definitions include various examples and/or forms of components thatfall within the scope of a term and that may be used for implementation.The examples are not intended to be limiting. Both singular and pluralforms of terms may be within the definitions.

“Computer-readable medium”, as used herein, refers to a medium thatparticipates in directly or indirectly providing signals, instructionsand/or data. A computer-readable medium may take many forms, including,but not limited to, non-volatile media, and volatile media. Non-volatilemedia may include, for example, optical or magnetic disks, and so on.Volatile media may include, for example, semiconductor memories, dynamicmemory, and so on. Common forms of a computer-readable medium include,but are not limited to, a floppy disk, a flexible disk, a hard disk, amagnetic tape, other magnetic medium, a CD-ROM, other optical medium, aRAM, a ROM, an EPROM, a FLASH-EPROM, or other memory chip or card, amemory stick, and other media from which a computer, a processor orother electronic device can read.

“Logic”, as used herein, includes but is not limited to hardware,firmware, software in execution, and/or combinations of each to performa function(s) or an action(s), and/or to cause a function or action fromanother logic, method, and/or system. Logic may include asoftware-controlled microprocessor, discrete logic (e.g., an applicationspecific integrated circuit (ASIC)), an analog circuit, a digitalcircuit, a programmed logic device, a memory device containinginstructions, and so on. Logic may include a gate(s), combinations ofgates, or other circuit components. Where multiple logical logics aredescribed, it may be possible to incorporate the multiple logical logicsinto one physical logic. Similarly, where a single logical logic isdescribed, it may be possible to distribute that single logical logicbetween multiple physical logics.

“Mobile Software Application”, as used herein, includes but is notlimited to, one or more computer or processor instructions in executionthat cause a computer, processor, or other electronic device to performfunctions, actions and/or behave in a desired manner. The instructionsmay be embodied in various forms including routines, algorithms,modules, methods, threads, and/or programs including separateapplications or code from dynamically linked libraries. Software,whether an entire system or a component of a system, may be embodied asan article of manufacture and maintained or provided as part of acomputer-readable medium as defined previously. Mobile software is asoftware that is executed and running on mobile devices. “User”, as usedherein, includes but is not limited to one or more persons, software,computers or other devices, or combinations of these.

FIGS. 1 and 2 illustrate exemplary systems and methods of mobiledatabase management and sharing, over private, secured, encryptednetworks, in real time. Disclosed embodiments comprise communicationdevices like tracking systems, microchip-based devices, and couldinclude any type of personal computing device such as a smartphone,tablet, etc. The database management and sharing systems discussedherein work on every computer-readable medium. At a high level,exemplary embodiments work as follows. The mobile database may store,for example, text, documents, media and/or multimedia data. As discussedin more detail herein, the mobile database may include additional logics(e.g., proxy objects) that may make the mobile database appear toprovide additional functionality typically associated with a morepowerful database. Exemplary embodiments recognize the database data,create database sharing requests, and communicate with other mobiledevices, worldwide over a private, secured network to transfer and storepart of the database item on other mobile devices.

An exemplary embodiment of a mobile database management and sharingsystem 500 comprises at least one mobile database 502 and one or moreelectronic circuits 10. The mobile database may reside on a mobile datacapture device. Typically, the electronic circuits 10 will be housed inmobile devices 40. More particularly, at least one mobile database 502and a proprietary Integrated Circuit (IC) 10 is installed within amobile device 40. The mobile database could be of any and all typesincluding but not limited to media, graphical, textual and securedcommunication information that is locally and remotely located. Themedia data may include one or more of digital image data, digital videodata, digital voice data, and digital music data.

In exemplary embodiments, the system 500 includes a database managementlogic 504 for analyzing and processing data received from a firstelectronic circuit l0a housed in the mobile device 40a of a first user.The database data may be analyzed according to its size and type. Asshown in FIG. 5 and the process flow diagram of FIG. 6, initially adatabase object or item 517 is created (step 1010). The system 500receives a database sharing request and splits the database object oritem 517 (e.g., a photo) to many segments (step 1020), which areillustrated in FIG. 5, according to an algorithm. More particularly, asshown in FIGS. 2 and 3, the mobile database management and sharingsystem 500 segments the mobile database 502 into a plurality of databasesegments 506, using its own segmentation algorithm 507, into a number ofsegments that is defined according to the database size and the mobiledevice memory. In exemplary embodiments, the database management logicindexes every database segment (step 1030). The segments may be storedin segment storage 511.

With reference again to FIGS. 2-3 and 6, the system also indexes theplurality of database segments using content-based analysis 509, buildsa unique segment ID 525 for each segment, and may store the segments ina designated table on the original mobile device where the object wascreated (step 1030). Alternatively, or in addition to local storage, thesystem may send one or more database segments to a second electroniccircuit over a private secured communication protocol. Moreparticularly, the mobile application software works in conjunction withthe electronic circuit l0a to index and send the database segments 506to other proprietary electronic circuits 10 that are installed on othermobile devices 40, worldwide, transparent to their users. This mayinclude sending a request to store the database segments on otherconnected mobile devices (step 1040). If another mobile device hasenough space to store the database segments (step 1050), the databasesegment will be stored on that mobile device (step 1060). If not, thatmobile device will be abandoned and mobile application software willsearch for another mobile device connected by the network 521 (step1070). The database management logic may control the database segmentssend and receive operations asynchronously. The proprietary IC is acomputing device including at least one arithmetic logic unit forexecuting instructions.

In exemplary embodiments, part of the database data may be stored in thelocal mobile device memory. The database segments 506 are encrypted andstored on one or more mobile device memories in the one or more mobiledevices 40. More particularly, the database segments 506 are encrypted519 and stored on local and other mobile devices' memories in an indexdatabase 513, worldwide and managed by the system and mobile applicationsoftware worldwide. In some embodiments, redundancy storage 515 may beassigned to certain mobile devices. A cache database 523 could bemaintained to hold recently accessed data and transactions so that theyare not lost due to connection failure, and a 3D model database 527 alsocould be provided.

Exemplary embodiments have a circuit logic 508 in communication with themobile database 502 for performing optimization of the allocation of thedatabase segments 506. This proprietary IC logic 508 performs constantmobile device optimization in order to allocate the database segments inthe most efficient way, enabling database sharing for all networkedmobile devices, worldwide. For instance, the system's IC logic 508 couldbe to selectively queue database segments 506 delivery to other mobiledevices 40, worldwide in order to achieve efficient database sharing.

Turning to FIG. 7, upon a user's request to retrieve or restore thedatabase item, the mobile device sends a request to restore the item(step 1110). The system 500 collects all database segments 506 from allproprietary ICs 10, and mobile device memory, worldwide, via itsprivate, secured, encrypted network. More particularly, in step 1120 thedatabase segments 506 are identified by an indexing table, and allmarked devices 40 are sent a request to provide the segments. If amobile device is not active, the segment can be restored from redundancybackup storage 515. That way, either mobile devices or the redundancybackup storage on the network send their segments 506 and the databaseobject is restored (step 1130).

In exemplary embodiments, the system 500 includes a circuit controllogic 510 in communication with the mobile database 502 for adjustingdatabase segmentation and send and receive parameters. The proprietaryIC control logic 510 works in conjunction with the mobile softwareapplication to automatically adjust the database segmentation, sendrate, receive rate and size according to the network and mobile servicebandwidth, mobile device memory capacity and performance. The system 500dynamically moves database segments between mobile devices 40 worldwideaccording to priority and proprietary IC and local mobile device memoryallocations. The database segments 506 are encrypted, secured and sentto other mobile device's IC's, to be stored on the proprietary IC'smemory unit and the mobile device internal memory, via private, securednetwork, worldwide.

Exemplary systems further comprise a database assembly logic 512 incommunication with the mobile database 502. The database assembly logic512 is configured to communicate with all mobile devices 40 to collectand assemble the mobile database 502 using one or more private channels514 (shown in FIG. 8) in parallel with transmission of the one or moreof the plurality of database segments 506. In exemplary embodiments, thesystem collects all segments from all mobile devices, worldwide, viaprivate, secured network and assembles the database item on the user'smobile device. The database assembly logic 512 may be configured toupdate the mobile database based, at the local mobile device memory.

In exemplary embodiments, the system 500 maintains real-time backups ofall database items. For instance, the system may maintain an up-to-datebackup of every database item on a central server 518. Moreparticularly, the database management logic 504 may record all thedatabase item's segments information in a backup table on a centralserver 518, via the network. In exemplary embodiments, there is back-endsoftware running on the central server 518, shown in FIG. 4. Theback-end software may include various artificial intelligence functions.

In exemplary embodiments, mobile database management and sharing system500 includes an error protocol to identify an action success, an actionfailure, or a cancellation request. Upon communication of errordetection the system may recover the data and repeat the segmentation,securing and sending protocol to ensure correct database data sharing.

In operation, exemplary mobile database management and sharingmethodology, illustrated in FIG. 6, employs a computer-readable mediumstoring integrated circuit units' instructions that when executed by aproprietary IC cause the proprietary IC to perform actions, theexecutable instructions comprising instructions for generating adatabase sharing request 516 that relates to some type of data stored inthe mobile database 502. For example, the database sharing request mightrequest sharing of one or more particular database segments 506. Thedata object could be a photo album or a file, and the file could be aphoto, an audio file, a video file, or a document. The metadata relatingto a photo could be a location, people, or objects in the photo. In oneexample, upon a user's database storage request relating to a photo or adocument, the proprietary IC that is working with a mobile softwareapplication invokes the database sharing request to split the databaseobject, in our case a photo, to many segments and, as discussed indetail herein, store each database segment on other mobile device aroundthe world.

The database sharing request 516 may be sent from one user's mobiledevice 40 and received by another mobile device, with each mobile devicecontaining the same proprietary IC and mobile database management andsharing system. In exemplary embodiments, the system sends the sharingrequest 516 to other mobile devices 40, worldwide, to store some of thedatabase segments on their proprietary IC and/or local memories. Next,the database sharing request 516 is processed by the mobile database 506and there may be a subsequent step of determining or confirming that thesharing requested was processed. The database sharing request 516 couldbe associated with remote processing of the database data in the mobiledatabase.

On each mobile device 40, the propriety IC 10 in conjunction with amobile application software analyzes the proprietary IC local memory andthe mobile device memory capacity and performance and approves ordisproves the request according to the analysis results. If the requestis not approved due to lack of memory, low performance or other reason,the request is automatically sent to other mobile devices until thenecessary number of mobile devices has been achieved. These servicerequests are performed via private, secured, encrypted communicationprotocol in real time by the proprietary IC that is working inconjunction with the mobile software application. Upon approval of thedatabase sharing request 516, the mobile device 40 stores the databasesegment 506 on the proprietary IC local memory and/or on the mobiledevice local memory.

In exemplary embodiments, the sharing request 516 is communicated to acentral server 518. The central server 518 is associated with providingservices to the mobile database and for transferring the database datato the central server. This communication may be done in parallel withtransmitting database data to the server including the requesteddatabase segments 506. The central server 518 may then send a databasesharing reply to the database sharing request 516, which would bereceived by the mobile device processing the request. That mobile device40 or the central server 518 would send the requested database segments506 to the mobile device that made the database sharing request 516.Exemplary methods also include running an error protocol and, if anerror is detected, recovering data, repeating the segmentation step, andrepeating the sending step.

In exemplary embodiments, database segments 506 are dynamically movedamong mobile devices 40, according to proprietary IC and local mobiledevices memory utilization to maintain efficient memory usage at alltimes. The system 500 may decide to move database segments betweenmobile devices according to memory capacity, mobile network bandwidthand mobile device performance. In the event of a mobile device downtimethe system 500 automatically recovers the missing segments 506 from thecentral backup server. At all times the database management and sharingsystem 500 maintains a dynamic indexing and status table per eachdatabase item and its segments for real time restoration.

In exemplary embodiments, each database segment 506 is indexed accordingto built-in table that is created by the database management system 500and stored on the main user's mobile device 40 that the database sharingrequest was sent from. The database management and sharing system isalso storing some of the database item's segment in the local mobiledevice memory. The user's mobile device that has sent the databasesharing request may store a segments indexing table with the list andlocation of all database item's segments, worldwide. The database data,including the requested database segments 506, may be encrypted andstored on one more mobile device memories in one or more mobile devices.The indexing table may be protected via 1024 encryption securityalgorithm.

In parallel the database management and sharing system 500 may save abackup of the database item on a fire-proof central server 518 forbackup recovering and restoring purposes. The backup, fire-proof centralservers are performing as a mirrored backup system to recover andrestore the entire database item or segments at any time. The system mayuse the backup system in case of a mobile device down scenario.

The user may request to restore the database item 517 (e.g., a photo)and the database management system 500 will send a restoration requestto all mobile devices 40 that store all the item's segments. Allsegments are then sent via secured, encrypted, private network protocolby the proprietary IC 10 and the mobile software application, to theuser's mobile device 40 and assembled to restore the database item 517(the photo). Since the system works in real time, the user doesn'tnotice the fact that the database object was stored on many mobiledevices around the world and rapidly restored on the mobile device.

The mobile database management and sharing system 500 natively searches,indexes, and processes database content according to proprietary expertsystem algorithms. Some of these functions may be performed on themobile device 40 on which the database item 517 is stored and some maybe executed on other mobile devices' proprietary ICs, as shown in theflow diagram of FIG. 6. Implementing a database sharing request queue onthe mobile device 40 and making it networked worldwide, shares thedatabase item 517 on other mobile devices 40 while still having thephysical records performed on the user's mobile device.

While the mobile database 502 and the database segments 506 may not becontinuously connected, either logically and/or physically, they may beconnected at times. When connected, database sharing requests queued onthe mobile database 502 and executed in turn by the database managementand sharing system 500, are transparent for the user. A database sharingresponse may selectively be provided back to the mobile database 502 byother mobile devices 40, worldwide, in turn.

In exemplary embodiments, the management and sharing methodology employsone or more proxy entities 520 related to the shared mobile database502. Mobile devices may be configured to become proxy entities 520. Asshown in FIG. 9, the mobile database 502 or database segments 506 aresent via mobile devices 40 as each one of them functions as a proxybetween mobile devices 40 creating a MESH network. More particularly,one or more of the requested database segments 506 are sent via one ormore mobile devices' proxy entities 520 to one or more separate mobiledevices 40. All mobile devices are transferring segments betweenthemselves. The database segments may be stored in the sending mobiledevice, the one or more separate mobile devices, as well as on a centralserver 518 or backup for redundancy purposes. In exemplary embodiments,each mobile device serves as a proxy entity 520 for others maintainingprocessing requests in a queue. More particularly, the database storageand sharing request is placed in a queue on mobile devices 40. The proxyentities 520, which may be mobile devices, then determine that thedatabase processing request is performed by a mobile device and, inresponse, generate a database sharing request, which may be associatedwith a media, textual or other electronic form processing request.

Exemplary methods may include determining whether to handle the databasestorage and sharing request locally, and/or globally over other mobiledevices, worldwide and transfer the database storage request to allselected mobile devices via private, secured communication protocol. Amedia service request may be transferred to multiple mobile devices 40so they work in conjunction, in real time, to store the requesteddatabase item. The mobile devices may then send a database storage replythat includes results to the database storage and sharing request andprovide a response to the database sharing request where the response isbased, at least in part on the database sharing reply.

Exemplary methods, illustrated in FIGS. 2, 3, 6 and 7, include receivingat the mobile database 502 a storage request from a mobile device 40,receiving at the mobile database segments data from the user's mobiledatabase, and starting a transaction. The methods may further includeprocessing the database sharing request on database segments data onselected other mobile devices' memory and proprietary IC to spread thedatabase item on many mobile devices, worldwide. The shared mobiledatabase 502 may contain a partial database of a whole databasecontained and managed via the database management and sharingmethodology. In addition, the shared mobile database 502 may beconfigured to be stored as segments 506 on many mobile devices' 40 localmemories and on a central server 518. Exemplary methods include the stepof generating an indexing table for all database segments that isaccessible to all selected mobile devices through a direct, private,secured communicating protocol and channel.

In exemplary embodiments, the executable instructions of thecomputer-readable medium include instructions for starting a firsttransaction before generating the database sharing and storing requestand ending the first transaction after generating the database sharingrequest. Alternatively, the instructions may be for starting a firsttransaction before receiving the database assembly processing requestand ending the first transaction after processing the database assemblyreply. In addition, there may be instructions for starting a secondtransaction before processing the database sharing and storing reply,processing the database storage reply, and ending the second transactionafter processing the database sharing reply. Instructions could also befor providing an assembly request to the mobile database based, at leastin part, on the database assembly reply, and generating a sequence ofdatabase assembly requests and a response to the assembly request.

Mobile database management and sharing methodology may further includequality control or error detection and correction mechanisms. Forexample, methods may further comprise determining that a mobile databasesegment 506 or other data item 517 may be out of synchronization betweenthe mobile database 502 and the other mobile devices database. If thedata item is determined to be out of sync, then there is a step ofautomatically configuring the database transmission reply as areconciliation, fixing request and waiting for a reconciliation responseassociated with the correction reply configured as a correction request.The correction may be processed in real time in to overcomecommunication errors.

As mentioned above, exemplary mobile database management and sharingsystems utilize local, mobile and/or cloud software in communicationwith the systems. In exemplary embodiments, a mobile softwareapplication manages database sharing and storage instructions inconjunction with a proprietary IC. When executed by the proprietary IC,the mobile app instructions cause the proprietary IC 10 to performcertain actions. For example, the instructions set may compriseinstructions configured for many of the steps described above. Theseinclude, but are not limited to, receiving a database storage request toperform a function by a mobile device 40 that includes a mobile database502. The mobile database 502 may act as a proxy for the database itemsharing and contain a partial database of a whole database contained andmanaged by the database sharing management system 500. The steps furtherinclude queuing the database storage request in a queue on the mobiledevice, determining whether to handle the database storage requestlocally, at the mobile database, and/or to transfer the database storagerequest to other mobile devices proprietary ICs and their local memorydatabase. This determination is based, at least in part, on whether thefunction can be performed on the partial database.

The steps may further include transferring the database storage requestfrom the queue to the database management system for segmentation of thewhole database and sending it to designated mobile devices worldwide inresponse to a determination that the database storage request isperformed on the partial database. Then the steps include receiving aresult, from the entire database, in response to the function beingperformed such that it appears that the function is performed by themobile database. The mobile app may also provide instructions forrecognizing database data stored by the mobile device and other mobiledevices and spreading the database segments through the proxy to othermobile devices to be stored on their proprietary IC and local memory,according to indexing setup.

In exemplary mobile app software, the determining step is further based,at least in part, on the proprietary IC configuration, a softwareconfiguration, a ratio of computing power, a load ratio, a communicationbandwidth, and/or a security measure. The communication with theproprietary IC and all other mobile devices' proprietary ICs may bebased on handshaking protocol for error correction. In exemplaryembodiments, the function of the mobile devices' search and selectionquery is directed to be performed on content in the mobile devicesdatabase, worldwide, which when executed, a dynamic of mobile devicesare selected according to their free local memory size, communicationbandwidth and performance. In exemplary embodiments, the databasestorage and sharing request is a search request and the function is asearch function to find dynamically mobile devices that are running thesame system to perform the database storage and sharing request locally.

As discussed above, exemplary systems and methods include one or morecommunication devices 40. A communication device 40 comprises anelectronic circuit 10. Any type of electronic circuit or microchip couldbe used and configured as described herein, including but not limitedto, a low noise amplifier (LNA) type circuit, a customized voltage-controlled oscillator (VCO) type circuit, a phase locked loop (PLL) typecircuit, a low pass filter (LPF) type circuit, a notch filter typecircuit, and/or a serializer and de-serializer (SERDES) type circuit.Proprietary electronic circuits are described in co-pending applicationSer. No. 15/015,441, filed Feb. 4, 2016, which is hereby incorporated byreference in its entirety.

Referring to FIG. 10, an exemplary electronic circuit 10 comprises aprocess subsystem 12 including a compliance circuit 13, a microprocessor15, an interrupt controller 17, and a bridge 19. The electronic circuit10 further comprises a control block 37 including a clock manager 39, areset manager 41, a power manager 43, and a system control 45. Theelectronic circuit also has a cryto-block 14 including a mastersub-block 51, a slave sub-block 53, a direct memory access circuit 55, apacket buffer 57, and one or more crypto-engines 59. An interconnect 61communicatively connects the process subsystem 12 to the control block37 and the crypto-block 14. The interconnect circuit 61 serves as ageneral interface to the various sub- blocks of the electronic circuit10.

The electronic circuit 10 may include one or more network connectionsthat can communicatively connect the electronic circuit to a publicnetwork of computers, which could be linked by the internet. One of thenetwork connections can communicatively connect the electronic circuit10 to a private network of computers, separate and distinct from thepublic network. The electronic circuit 10 may include a memoryunit/controller 31 comprised of a memory controller circuit. An externalmemory interface 33 may be in communication with the memory unit 31 viaa memory interface port. In exemplary embodiments, the electroniccircuit 10 may further comprise a radio unit 83 (shown in FIG. 13) andan antenna 19 embedded within the electronic circuit and/or locatedoutside the electronic circuit and communicatively connected to theelectronic circuit.

Exemplary electronic circuit architecture may be arranged to have someforms of a public unit and a private unit. A barrier may be locatedbetween the public unit and the private unit. The public unit mayinclude a network connection that can communicatively connect theelectronic circuit 10 to a public network of computers, which could belinked by the internet. A second network connection may be locatedwithin the private unit. The second network connection cancommunicatively connect the electronic circuit 10 to a private networkof computers, separate and distinct from the public network. The networkconnections can be wireless or wired connections. For additionalsecurity, the second network connection may be a wired connection to theprivate network, and the private unit may also be configured so itcannot connect to the internet. In exemplary embodiments, the privateunit is not connected to the internet and the public unit is connectedto the internet.

A barrier may be located between the public and private units,sub-blocks, or groups of sub-blocks. It should be noted that the barrieris not necessarily located physically between the two units, sub-blocks,or groups of sub-blocks; rather, it stands between them forcommunication purposes, separating the private unit from the public unitfor security while at appropriate times serving as an interconnect tocommunicatively connect the two units. The barrier may also separate thefirst and second network connections. More particularly, the barrier maybe an inner hardware-based access barrier or inner hardware-basedfirewall. An exemplary barrier has a signal interruption mechanism toprevent communications between the private and public units, sub-blocks,or groups of sub-blocks when necessary or desirable. In exemplaryembodiments, the signal interruption mechanism is a bus having an on/offswitch that controls communication input and output.

In exemplary embodiments an electronic circuit 10 forms an integral partof mobile database management and sharing system 500 comprising one ormore personal computing devices 40. In exemplary systems, each personalcomputing device 40 houses an electronic circuit 10. More particularly,the electronic circuit or microchip 10 can be embedded within a mobiledevice's existing microchip or installed within a mobile device'selectronic board, as an integral part of the system, and be configuredto operate as a specific purpose electronic circuit or microchip.Alternatively, the electronic circuit or microchip 10 could be part of acomplete, independent computer system within a mobile device. In FIG. 2,satellite communications are represented by solid lines and electroniccircuit communications by dashed lines.

In exemplary embodiments, the communication device is a tracking device.With reference to FIGS. 11-14, exemplary embodiments of a trackingdevice 200 comprise a package 202 with an electronic circuit 10 embeddedtherein. The package 202, also referred to as a “patch” or patchpackage, may be made of or coated with a sticky material so its outersurface is sticky. The patch package 202 is made of a flexible andlightweight but rugged material such as a polymer-based or plasticmaterial or any other material that provides both flexibility andstrength. In exemplary embodiments, the patch package 202 is made of amaterial that is waterproof and otherwise weatherproof so it is notdamaged in inclement weather and protects the electronic circuit 10 andother electronics contained in the device 200.

The stickiness of the package 202 advantageously serves to enable thetracking device 200 to be affixed to an object as a patch product whichcan track the object anywhere. As described in more detail herein, whenactivated by pressing the start button 203, the electronic circuit 10within the tracking device 200 transmits signals to enable tracking ofthe device's location anywhere on Earth. As best seen in FIGS. 3A and3B, an affix sensor 204 may be provided with the tracking device 200.The affix sensor 204 is an advanced circuitry including an affix circuit217 that controls the device's mounting and removal responses and may beintegrated with the electronic circuit 10 or a separate component incommunication with the electronic circuit 10.

Advantageously, the affix sensor 204 determines whether the trackingdevice 200 is affixed to the object to be tracked, and in exemplaryembodiments the tracking device automatically turns on when affixed toan object. In exemplary embodiments, the “peel-and-stick” sensor systemincludes an adhesive 205 to stick to an object and pressure sensors 211and conductivity sensors that detect application to the object and startthe device's operation. It will stay on that object for the rest of thedevice's life and, once attached to an object, an internal clock startsto work. The clock has several tasks, one of which is determining thedevice's lifetime. Advantageously, the affix sensor can also determineif the device 200 gets removed from the object.

As shown in FIGS. 11-13, the tracking device 200 also includes anantenna 206 to facilitate communications. More particularly, thetracking device 200 may include an antenna 206 and control circuitryconfigured to control transmission and receipt of broadband informationto and from the antenna 206. Antenna 206 may be integrated with theelectronic circuit 10 or be a separate component in communication withthe electronic circuit 10. The antenna may be any form or type ofantenna such as a wire antenna 206 or a ball antenna. The ball-basedstructure advantageously provides more power in a miniature antennastructure for use with various wave lengths in smaller scales.

Thus, it is seen that systems and methods of mobile database managementand sharing are provided. It should be understood that any of theforegoing configurations and specialized components or connections maybe interchangeably used with any of the systems of the precedingembodiments. Although illustrative embodiments are describedhereinabove, it will be evident to one skilled in the art that variouschanges and modifications may be made therein without departing from thescope of the disclosure. It is intended in the appended claims to coverall such changes and modifications that fall within the true spirit andscope of the present disclosure.

What is claimed is:
 1. A mobile database management and sharing system,comprising: at least one mobile database; and a first electronic circuitin communication with the mobile database, the electronic circuitincluding a controller, a secured basic input/output (BIOS) system, amemory unit, a radio unit, and an antenna; wherein the system segmentsthe mobile database into a plurality of database segments; wherein thesystem indexes the plurality of database segments; and wherein thesystem sends one or more of the plurality of database segments to asecond electronic circuit over a private secured communication protocol.2. The system of claim 1 wherein one or both of the first and secondelectronic circuit is an integrated circuit.
 3. The system of claim 1wherein one or both of the first and second electronic circuit is housedwithin one or more mobile devices.
 4. The system of claim 1 furthercomprising a database management logic in communication with the mobiledatabase for analyzing and processing data received from the firstelectronic circuit.
 5. The system of claim 1 further comprising acircuit logic in communication with the mobile database for performingoptimization of allocation of the plurality of database segments.
 6. Thesystem of claim 1 further comprising a circuit control logic incommunication with the mobile database for adjusting databasesegmentation and send and receive parameters.
 7. The system of claim 3wherein the plurality of database segments is encrypted and stored onone more mobile device memories in the one or more mobile devices. 8.The system of claim 3 further comprising a database assembly logic incommunication with the mobile database configured to communicate withthe one or more mobile devices to collect and assemble the mobiledatabase using one or more private channels in parallel to sending theone or more of the plurality of database segments.
 9. The system ofclaim 1 further comprising cloud software in communication with thesystem.
 10. A method of mobile database management and sharing,comprising: processing data received from at least one mobile devicecontaining at least one electronic circuit; segmenting a mobile databaseinto a plurality of database segments; indexing the plurality ofdatabase segments; processing a database sharing request received fromat least one mobile device, the database sharing request requestingsharing of one or more of the plurality of database segments; sendingthe one or more of the plurality of database segments requested to atleast one mobile device over a private secured communication protocol.11. The method of claim 10 further comprising communicating the databasesharing request to a central server.
 12. The method of claim 11 furthercomprising communicating database data to the central server in parallelwith the database sharing request.
 13. The method of claim 11 furthercomprising receiving a reply to the database sharing request from thecentral server.
 14. The method of claim 10 further comprising runningback-end software on a central server.
 15. The method of claim 10further comprising running an error protocol.
 16. The method of claim 15further comprising detecting an error, recovering data, repeating thesegmentation step, and repeating the sending step.
 17. The method ofclaim 14 wherein the back-end software includes artificial intelligence.18. A mobile device containing a database management and sharing system,comprising: a shared mobile database; one or more proxy entities relatedto the shared mobile database; an electronic circuit in communicationwith the shared mobile database and the one or more proxy entities, theelectronic circuit including a controller, a secured basic input/output(BIOS) system, a memory unit, a radio unit, and an antenna; and mobilesoftware executed and running on the mobile device; wherein the systemsegments the shared mobile database into a plurality of databasesegments; wherein the system indexes the plurality of database segments;and wherein at least some of the plurality of database segments are sentvia the one or more proxy entities to one or more separate mobiledevices and stored in the mobile device and the one or more separatemobile devices.
 19. The mobile device of claim 18 wherein the pluralityof database segments is also stored on a central server.
 20. The mobiledevice of claim 18 wherein the one more proxy entities maintainprocessing requests in a queue.
 21. The mobile device of claim 18wherein the shared mobile database contains a partial database of awhole database contained and managed by the database management andsharing system.
 22. The mobile device of claim 18 wherein the mobilesoftware contains artificial intelligence.
 23. A method of sharing data,comprising: generating a database sharing request received from at leastone mobile device, the database sharing request relating to data in amobile database; determining that the database sharing request isprocessed by the mobile database; communicating the database sharingrequest to a central server; communicating database data to the centralserver in parallel with the database sharing request; and receiving areply to the database sharing request from the central server.
 24. Themethod of claim 23 further comprising encrypting the database data andstoring the database data on one more mobile device memories in one ormore mobile devices.